Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Don't call setUser on transaction if there is no user logged in. This... #9

Merged
merged 1 commit into from
Feb 12, 2013

Conversation

chrisrossi
Copy link
Member

... could

cause the username set on the transaction to be a strange string: " None".

…is could

cause the username set on the transaction to be a strange string: " None".
@mmerickel
Copy link
Member

Should this be left unset, or should some placeholder be set as the user? I'm not familiar with setUser on a transaction.

@chrisrossi
Copy link
Member Author

Well if you look in the transaction code, Transaction.user defaults to '',
which should be a safe value.

Chris

On Tue, Feb 12, 2013 at 11:40 AM, Michael Merickel <notifications@github.com

wrote:

Should this be left unset, or should some placeholder be set as the user?
I'm not familiar with setUser on a transaction.


Reply to this email directly or view it on GitHubhttps://github.com//pull/9#issuecomment-13441744.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants